Skip to content

Revert "Replace E2 VMs with N4 across example blueprints"#5424

Merged
aslam-quad merged 1 commit intodevelopfrom
revert-5406-fix/e2-n4
Mar 30, 2026
Merged

Revert "Replace E2 VMs with N4 across example blueprints"#5424
aslam-quad merged 1 commit intodevelopfrom
revert-5406-fix/e2-n4

Conversation

@aslam-quad
Copy link
Copy Markdown
Contributor

Reverts #5406

@aslam-quad aslam-quad requested review from a team and samskillman as code owners March 30, 2026 04:32
@github-actions github-actions bot added the external PR from external contributor label Mar 30, 2026
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request restores the previous configuration for machine types across multiple example blueprints and validation test files. The change ensures consistency by reverting recent updates that had migrated these configurations to N4 machine types, returning them to their original E2 specifications.

Highlights

  • Reversion of Machine Types: This pull request reverts the previous change that updated various example blueprints and test configurations from E2 machine types back to N4 machine types.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@aslam-quad aslam-quad added the release-chore To not include into release notes label Mar 30, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request performs a comprehensive update across the repository, replacing n4-standard machine types with e2-standard equivalents. This change affects numerous YAML blueprints, Terraform modules, documentation files, and cloud build test configurations. I have no feedback to provide.

@aslam-quad aslam-quad merged commit 8abc1fc into develop Mar 30, 2026
12 of 77 checks passed
@aslam-quad aslam-quad deleted the revert-5406-fix/e2-n4 branch March 30, 2026 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

external PR from external contributor release-chore To not include into release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants